as 
, wherein, 
is system bandwidth; Please refer to RP-243290 for detailed scope of the WI for LTE-based 5G Broadcast Phase 2.
R1-2501552 Session notes for 9.13 (LTE-based 5G Broadcast Phase 2) Ad-Hoc Chair (Huawei)
Friday decision: The session notes are endorsed and contents reflected below.
[120-R19-Broadcast] – Jordi (EBU)
Email discussion on Rel-19 LTE-bad 5G Broadcast Phase 2
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2501057 Introduction of WI “Time and Frequency Interleaving for LTE-based 5G Terrestrial Broadcast” EBU
R1-2500148 Discussion on time-frequency interleaver design for LTE-based 5G Broadcast ZTE Corporation, Sanechips
R1-2500150 On time-frequency interleavers for LTE-based 5G Broadcast Huawei, HiSilicon
R1-2500582 Design of Time and Frequency Interleaver for LTE-based 5G Broadcast Shanghai Jiao Tong University
R1-2500872 Time-frequency interleaver design for MBMS dedicated cells Samsung
R1-2501058 Details of Time and Frequency Interleaving for LTE-based 5G Terrestrial Broadcast EBU
R1-2501179 Time and Frequency Interleaving for 5G Broadcast Qualcomm Incorporated
R1-2501432 FL summary#1 on Rel-19 LTE-based 5G Broadcast Phase 2 Moderator (EBU)
From Tuesday session
Agreement
For TBS scaling by N, down-select one of the two options below:
·
Option
1: Calculate the total number of PRBs as , wherein, is system bandwidth;
o
If
, reuse the transport block size
table in TS 36.213 and according to the obtained 
and , obtain the corresponding TBS;
o
Else, reuse the transport block size
table in TS 36.213 and according to the obtained and , obtain the corresponding TBS’;
and calculate the final TBS as 
o The operation “round{x}” is mapping x to the closest TBS from all the existing TBS values in section 7.1.7.2 TS 36.213.
·
Option
2: Obtain the initial TBS (
as per current
specifications, and calculate the final TBS as
o The operation “round{x}” is mapping x to the closest TBS from all the existing TBS values in section 7.1.7.2 TS 36.213.
Agreement
At least values of N={1,4,8} are supported, where N=1 indicates time interleaving is disabled.
· FFS: other values
Agreement
LBRM is applied for MCH (excluding MCCH and MSI) with time interleaving.
· FFS spec impact
Agreement
For PMCH with time interleaving, the maximum TBS a UE supports for the scaled TB is derived based on DL-SCH as per TS 36.306 set by UE category.
· FFS when the UE category has multiple maximum TBS
Agreement
The maximum number of transport block bits received within a TTI defined by the UE category should include the number of bits for unicast and broadcast, where the number of bits for broadcast is the one after being scaled up by N.
Agreement
The basic transmission pattern of PMCH with time interleaving consists of a set of (M x N) consecutive MBSFN subframes, excluding MCCH and MSI, where two transmissions of the same TB are separated by (M-1) MBSFN subframes, excluding MCCH and MSI.
Agreement
Specify time interleaving per MBMS session/MTCH without supporting interleaving across different MBMS sessions/MTCH.
Agreement
Regarding configuration for time interleaving transmission, the following options can be considered:
· Option 1: Per MBSFN area/MCCH configuration, e.g., via mcch-Config
· Option 2: Per PMCH configuration, e.g., via pmch-Config
· Option 3: Per MBMS session, e.g., via MBMS-SessionInfo or via MAC CE
Agreement
RAN1 to further study the potential issue of mismatch between MSI periodicity and the basic transmission pattern of (M x N) subframes.
Agreement
The equation of k0 for time interleaving is modified to avoid puncturing of systematic bits.
·
Further
study the exact equation for k0 for the n-th subframe of a transmission
belonging to a same TB 
, 
), including
o
Option
1: for each CB of the TB, 
, where 
(as per TS 36.212), and
is the redundancy
version of the n-th subframe.
o
Option
2: For each CB of the TB, follow the principle of NR TBoMS to determine
o
Option
1 and Option 2 assumes all CBs of the TB have the same RV index for all CBs of
the TB, indexed by
·
FFS
whether different CBs of the TB mapped to each subframe may have different RV
indices (e.g., indexed by different per CB)
Agreement
The
modulation symbol vector (prior to frequency interleaving) 
is interleaved,
according to the principles of subclause 5.1.4.1.1 of TS 36.212 as follows
, set the number of
rows 
to be the minimum
integer satisfying 
, where Z is the number of data REs in
one OFDM symbol
with 
elements, as
required, to obtain 
into the 
-matrix
column-wise, with 
in column 0 of row
0.
by reading the
elements of the above -matrix row-wise,
excluding the 
. shall then be
mapped to resource elements, according to clause 6.3.5 of TS 36.211.FFS: whether to apply a cyclic shift offset, and the details of the cyclic shift offset for the concatenated frequency interleaver outputs of all OFDM symbols before the mapping to REs of a subframe, where the cyclic shift offset is dependent on the RV index.
Agreement
The granularity of the frequency interleaver is 1 RE.
R1-2501433 FL summary#2 on Rel-19 LTE-based 5G Broadcast Phase 2 Moderator (EBU)
From Thursday session
Agreement
For TBS scaling by N, the following is clarified for the rounding operation in option 1 and option 2 in previous agreement:
·
In case two TBSs are at the
same distance of 
, the larger TBS is chosen.
Agreement
Regarding configuration for time interleaving transmission, the following options can be considered:
·
Option 1:
Per MBSFN area/MCCH configuration, e.g., via mcch-Config
· Option 2: Per PMCH configuration, e.g., via pmch-Config
· Option 3: Per MBMS session, e.g., via MBMS-SessionInfo or via MAC CE
Agreement
Values of M = 16 and M = 8 are supported.
· FFS other values
· Note: some UE categories and depending on factors such as (value of N, bandwidth, MCS) may not be able to receive an interleaved MTCH with M=16.
Agreement
The previous agreement is modified as follows:
The modulation
symbol vector (prior to frequency interleaving) 
is
interleaved, according to the principles of subclause 5.1.4.1.1 of TS 36.212 as
follows
·
Set the number of columns of the frequency
interleaver, 
, set
the number of rows 
to be
the minimum integer satisfying 
, where Z is the number of
data REs in one OFDM symbol
o FFS: How to determine X
§ Option 1: X is equal to the number of codeblocks that are mapped to the OFDM symbol
§ Option 2: X=32
§ Other options are not precluded.
·
Append 
with 
elements,
as required, to obtain 
·
Write the elements of into
the 
-matrix
column-wise, with 
in
column 0 of row 0.
· FFS whether the rows and elements in each row will be permuted, with details to be further studied, e.g., intra-row cyclic shifts, inter-row permutations
·
Obtain the vector 
by
reading the elements of the above -matrix
row-wise, excluding the 
.
·
The vector shall
then be mapped to resource elements, according to clause 6.3.5 of TS 36.211.
FFS: whether to apply a cyclic shift offset, and the details of the cyclic shift offset for the concatenated frequency interleaver outputs of all OFDM symbols before the mapping to REs of a subframe, where the cyclic shift offset is dependent on the RV index.
Guidance for the next meeting:
To evaluate frequency interleavers, the “Two Path Ensemble” channel profile defined in Table A.1.1, Annex A of A325-2024-04” (with delay to be selected by proponents but less than 0.95*CP) can be used by companies.
Please refer to RP-250794 for detailed scope of the WI for LTE-based 5G Broadcast Phase 2.
Rapporteur to provide initial input on higher layer signalling under agenda item 9.13. For input on higher layer signalling from any other source, please include it as part of your tdoc to relevant sub-agenda items.
R1-2503117 Session notes for 9.13 (LTE-based 5G Broadcast Phase 2) Ad-Hoc Chair (Huawei)
Friday decision: The session notes are endorsed and contents reflected below.
[120bis-R19-Broadcast] – Jordi (EBU)
Email discussion on Rel-19 LTE-bad 5G Broadcast Phase 2
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2502548 Higher layer parameters for Rel-19 LTE-based 5G Broadcast after RAN1#120 EBU
R1-2501912 Discussion on time-frequency interleaver design for LTE-based 5G Broadcast ZTE Corporation, Sanechips
R1-2502209 On time-frequency interleavers for LTE-based 5G Broadcast Huawei, HiSilicon
R1-2502390 Views on LTE-based 5G broadcast Samsung
R1-2502546 Further details on open issues regarding TFI for LTE-based 5G Broadcast EBU
R1-2502582 Design of Time-frequency interleaver for 5G Broadcast Shanghai Jiao Tong University
R1-2502861 Time and Frequency Interleaving for 5G Broadcast Qualcomm Incorporated
R1-2503001 FL summary#1 on Rel-19 LTE-based 5G Broadcast Phase 2 Moderator (EBU)
From Monday session
Agreement
Support at least the following values of time interleaver depth:
R1-2503002 FL summary#2 on Rel-19 LTE-based 5G Broadcast Phase 2 Moderator (EBU)
From Tuesday session
Agreement
In case of time interleaving, in order to reduce the resource wastage due to the potential mismatch between MSI periodicity and the (MxN) pattern:
Agreement
The number of columns, 
, of the frequency interleaver is 
, where 
denotes the number of CBs in the TB (including scaling, if any), 
denotes the number of OFDM symbols of the PMCH,
, and 
denotes the operation to compute the greatest common divisor.
Agreement
The following steps are applied to the rows of the frequency interleaver:
1.
Perform inter-row permutation with a reorder of the row indexes 
, which is calculated as:
With
, 
, and 
2. Perform a cyclic shift to the elements in the j-th row with an offset S(j) defined as:
R1-2503003 FL summary#3 on Rel-19 LTE-based 5G Broadcast Phase 2 Moderator (EBU)
From Wednesday session
Agreement
LBRM parameters (e.g. 
) are
consistent between the broadcast network and the (multiple) UEs that are
receiving the broadcast transmission.
, .
Agreement
The agreement in the previous meeting is updated as follows:
Regarding configuration for time interleaving transmission, the following options can be considered:
· Option 1: Per PMCH configuration, e.g., via pmch-Config
· Option 2: Per MBMS session, e.g., via MBMS-SessionInfo or via MAC CE
o Alt1: If per MBMS session configuration is done, a T_proc of 3 ms between the end of the MSI and the first MTCH in the MCH scheduling period is needed for UE de-rate matching.
o Alt2: If per MBMS session configuration is done, other options (than Alt1 above) are not precluded, e.g. that allow the UE to know the M, N values of the first MTCH scheduled after the MSI
Agreement
Obtain the initial TBS (𝑇𝐵𝑆′) as per current specifications, and calculate the final TBS as 𝑇𝐵𝑆=𝑟𝑜𝑢𝑛𝑑{𝑇𝐵𝑆′×𝑁}.
· The operation “round{x}” is mapping x to the closest TBS from all the existing TBS values in section 7.1.7.2 TS 36.213.
R1-2503143 Final summary on Rel-19 LTE-based 5G Broadcast Phase 2 Moderator (EBU)
Please refer to RP-250794 for detailed scope of the WI for LTE-based 5G Broadcast Phase 2.
Rapporteur to provide initial input on higher layer signalling under agenda item 9.13. For input on higher layer signalling from any other source, please include it as part of your tdoc to relevant sub-agenda items.
R1-2504899 Session notes for 9.13 (LTE-based 5G Broadcast Phase 2) Ad-Hoc Chair (Huawei)
Endorsed and incorporated below.
[121-R19-Broadcast] Email discussion on Rel-19 LTE-bad 5G Broadcast Phase 2 – Jordi (EBU)
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2504652 Higher layer parameters for Rel-19 LTE-based 5G Broadcast after RAN1#120 EBU
R1-2503249 On time-frequency interleavers for LTE-based 5G Broadcast Huawei, HiSilicon
R1-2503332 Discussion on time-frequency interleaver design for LTE-based 5G Broadcast ZTE Corporation, Sanechips
R1-2503589 Further details on Time and Frequency Interleaving for 5G Broadcast phase-2 Samsung
R1-2504241 Further discussion on open issues regarding TFI for LTE-based 5G Broadcast EBU
R1-2504417 Time and Frequency Interleaving for 5G Broadcast Qualcomm Incorporated
R1-2504654 Time and Frequency Interleaving for 5G Broadcast Qualcomm Incorporated
R1-2504732 FL summary#1 on Rel-19 LTE-based 5G Broadcast Phase 2 Moderator (EBU)
Agreement
For each CB of the TB, 
, where 
(as per TS 36.212), and 
is the redundancy version of the n-th subframe, where 
, and, 
values are
mapped sequentially to subframes, i.e., 
.
Agreement
Time interleaving parameters are indicated
per PMCH configuration, e.g., via a configuration of 
in pmch-Config. Specify the following set of new MSI periodicities:
{rf7, rf14, rf53, rf56, rf112, rf424}.
- Additionally down-select among {rf27 or rf28}, {rf106 or rf108}, {rf211 or rf212}.
-
FFS actions on the residual
mismatch after applying the new MSI periodicities in conjunction with the
configuration of
o
Option 1: Fill the
residual space with a service with different TFI configuration 
, e.g., via an
additional (addressing the residual space) configuration via pmch-Config
Agreement
The soft buffer size for one time-interleaved TB is down-selected from
-
Option 1: 
, where:
o
Option 1a: 
is the soft buffer size pertaining to a reference UE category, M
is the number of TBs for time-interleaving and 
is a scaling factor. FFS: exact value/values/configuration of .
o
Option 1b: is configured in PMCH-Config from {1827072, 3654144, 5481216,
7308288, 9744384, 12789504, 14616576, 17052672, 19488768, 24360960, 29233152,
34105344, 36541440, 38977536, 42631680, 47431680, 303562752}, 
is configured in PMCH-Config from: {1, 3/2, 6/5, 8/5, 2, 12/5, 8/3,
3, 5, 32}; and M is the number of TBs for time-interleaving.
-
Option 2 : The soft
buffer size for the code block is denoted as 
, where 
and 
are same as defined in TS 36.212 clause 5.1. 
is calculated based on, e.g., 
, 
, N.
o
FFS: Details of determining
(e.g., based on a notion of maximum coding rate) may need to be
considered, to provide the flexibilities afforded by the LTE specifications,
keeping in mind the LTE UE categories.
- FFS: impact to soft buffer size for UE receiving unicast considering the case where UE prioritizes receiving broadcast.
Agreement
Confirm the working assumption in the following agreement:
Agreement
The number of
columns, 
, of the frequency interleaver is 
, where 
denotes the number of CBs in the TB (including scaling, if any), 
denotes the number of OFDM symbols of the PMCH,
- Working assumption:
o
m = 
, and 
denotes the operation to compute the greatest common divisor.
Agreement
For PMCH with time interleaving, the maximum TBS a UE supports for the scaled TB is down-selected from the following:
- Option 1: the largest TBS among the multiple maximum TBS of a DL-SCH as per TS 36.306 set by UE category.
- Option 2: the smallest TBS among the multiple maximum TBS of a DL-SCH as per TS 36.306 set by UE category.
- Option 3: signalled by the UE from the multiple maximum TBS of a DL-SCH as per TS 36.306 set by UE, e.g. using a new UE capability
R1-2504733 FL summary#2 on Rel-19 LTE-based 5G Broadcast Phase 2 Moderator (EBU)
Agreement
Add the following MSI periodicities to the previous RAN1 agreement {rf28, rf108, rf212}.
Agreement
The residual space
created by the mismatch between (M,N) and the MSI periodicity may be filled
with the last MTCH service with different TFI configuration , e.g., via an
additional (addressing the residual space) optional configuration via
pmch-Config.
-
In the space before
mismatch, all MTCHs within the MSI period have the same (M,N) obtained via the configuration of in pmch-Config.
Agreement
The soft buffer size for one time-interleaved TB is down-selected from
-
Option 1: , where:
o
Option
1a: is
the soft buffer size pertaining to a reference UE category, M is the
number of TBs for time-interleaving and 
is a scaling factor configured from network among values in
the interval [0 1]. FFS: the exact values in the interval.
o
Option
1b: is configured in PMCH-Config from
{1827072, 3654144, 5481216, 7308288, 9744384, 12789504, 14616576, 17052672,
19488768, 24360960, 29233152, 34105344, 36541440, 38977536, 42631680, 47431680,
303562752}, is configured in PMCH-Config from: {1,
3/2, 6/5, 8/5, 2, 12/5, 8/3, 3, 5, 32}; and M is the number of TBs
for time-interleaving.
- FFS: impact to soft buffer size for UE receiving unicast considering the case where UE prioritizes receiving broadcast.
Agreement
The number of subframes used for time-interleaving derived from ‘stop MTCH (x+1)’ is expected to be an integer multiple of MxN.
- FFS: spec impact, if any
R1-2504734 FL summary#3 on Rel-19 LTE-based 5G Broadcast Phase 2 Moderator (EBU)
Agreement
Cyclically shift the bit sequence 
in Section 6.3.1 of TS 36.211 for the 
subframe of the time-interleaved TB by 
bits, where
,
denotes the number of subframes to which the time-interleaved TB is
mapped
-
is
o
Alt 1: 
, with 
§
is the number of bits in the 
codeblock within a subframe (as defined in TS 36.212)
o
Alt 2: , with 
§
denotes the number of OFDM symbols within a subframe
denotes the number of CBs in the time-interleaved (scaled) TB
§
is the number of bits in the codeblock within a subframe (as defined in TS 36.212)
A new RRC parameter configures between and as above
§ If this new RRC parameter is not configured, the cyclic shift described in this agreement is not enabled.
§ A new optional UE capability is introduced to indicate support of this cyclic shift.
§ FFS: Extension of the bit-field corresponding to this RRC parameter by one additional bit, based on NOTE 1 below
o
NOTE 1: The following
alternative for may be considered, exclusively based on BLER-vs-SNR performance
comparison (with respect to Alt 1 / Alt 2)
§
, with 
§
Where 
is the number of subcarriers available in 1 OFDM symbol for PMCH,
e.g. 
Agreement
The soft buffer size for one
time-interleaved TB is calculated as , where
is the soft buffer size configured according to a reference UE
category, indicated from among { DL Cat4, DL Cat5, … DL Cat26}, M is the
number of TBs for time-interleaving and β is configured from: {1/32, 1/5,
1/3, 3/8, 5/12, 1/2, 5/8, 5/6, 2/3, 1}.
Agreement
Rel-19 IE in MBMS Interest Indication message carries following parameters utilized for receiving Rel-19 LTE-based 5G Broadcast service(s):
· Frequency
· New values of sub-carrier spacing = {2.5 kHz, 1.25 kHz}
· New values for bandwidth = {n30, n35, n40}
· A new UE baseband resource Scaling factor (e.g., utilized soft buffer at the UE) used for receiving the time interleaved broadcast
Agreement
In case the time interleaved PMCH transmission (as configured) exceeds a UE’s capability(/es) in terms of soft buffer size or maximum TBS supported in a TTI, the UE is not expected to receive the corresponding time interleaved PMCH transmission.
Agreement
Update of the FFS of a previous agreement:
Agreement
The number of subframes used for time-interleaving derived from ‘stop MTCH (x+1)’ is expected to be an integer multiple of MxN.
Spec impact is up to RAN2.
Agreement
RAN1 asks RAN2 whether/how to address the HARQ handling in the MAC specification for the Rel-19 time-interleaved PMCH transmission with M TBs and N RVs.
Agreement
For clarification to RAN2:
When time-interleaving is enabled, values of N for configuration/indication do not include N=1. When N is not configured, time-interleaving is disabled i.e. N=1.
R1-2504921 RAN2 aspects on LTE-based 5G Broadcast Phase 2 EBU
R1-2504922 RAN2 aspects on LTE-based 5G Broadcast Phase 2 RAN1, EBU
Agreement
LS on RAN2 aspects on LTE-based 5G Broadcast Phase 2 is agreed. Final LS in R1-2504922.